Skip to content

Add Australian PFTs#21

Merged
Whyborn merged 3 commits intomainfrom
add-aus-PFTs
Jan 20, 2026
Merged

Add Australian PFTs#21
Whyborn merged 3 commits intomainfrom
add-aus-PFTs

Conversation

@Whyborn
Copy link
Collaborator

@Whyborn Whyborn commented Jan 6, 2026 •
edited by github-actions bot
Loading

Adds Aus PFTs to the AM3 JULES infrastructure. Should lead to no functional changes, as the PFT maps do not have any fractions assigned to tiles 12 and 13, and there is no meaningful science associated with the tiles either. Effectively just a renaming of empty1 and empty2 in various locations to aust_mesic and aust_xeric.

🚀 The latest prerelease access-am3/pr21-1 at b2f17f2 is here: #21 (comment) 🚀

🚀 The latest prerelease access-am3/pr21-2 at 029ded7 is here: #21 (comment) 🚀

@github-actions
Copy link

github-actions bot commented Jan 6, 2026

The model version in the ./spack.yaml has not been updated.
You can update it manually.

@github-actions
Copy link

github-actions bot commented Jan 6, 2026

🚀 Attempted to deploy access-am3 Prerelease pr21-1 with commit de91193

🖥️ Gadi Deployment ❌

@Whyborn Whyborn temporarily deployed to Gadi Prerelease January 6, 2026 03:05 — with GitHub Actions Inactive
@github-actions
Copy link

github-actions bot commented Jan 6, 2026

🚀 Attempted to deploy access-am3 Prerelease pr21-1 with commit b2f17f2

🖥️ Gadi Deployment ✔️

Usage Instructions

access-am3, defined in ./spack.yaml, will be deployed to Gadi as:

  • 2026.01.000 as a Release (when merged).
  • pr21-1 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-am3/pr21-1

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the access-am3-pr21-1 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

If the above was not what was expected, commit changes to config/versions.json in this PR.

ccarouge
ccarouge requested changes Jan 19, 2026
View reviewed changes
Copy link
Member

@ccarouge ccarouge left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See comment. Since it can't go ahead like this, I'm setting request changes.

@Whyborn Whyborn temporarily deployed to Gadi Prerelease January 19, 2026 04:13 — with GitHub Actions Inactive
@github-actions
Copy link

github-actions bot commented Jan 19, 2026

🚀 Attempted to deploy access-am3 Prerelease pr21-2 with commit 029ded7

🖥️ Gadi Deployment ✔️

Usage Instructions

access-am3, defined in ./spack.yaml, will be deployed to Gadi as:

  • 2026.01.000 as a Release (when merged).
  • pr21-2 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-am3/pr21-2

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the access-am3-pr21-2 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

If the above was not what was expected, commit changes to config/versions.json in this PR.

@Whyborn Whyborn requested a review from ccarouge January 19, 2026 05:09
JhanSrbinovsky
JhanSrbinovsky approved these changes Jan 19, 2026
View reviewed changes
Copy link
Collaborator

@JhanSrbinovsky JhanSrbinovsky left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

2026 already!

@Whyborn
Copy link
Collaborator Author

Whyborn commented Jan 19, 2026

@ccarouge seems it won't let me merge until you give it the OK again, despite making the changes

ccarouge
ccarouge approved these changes Jan 20, 2026
View reviewed changes
Copy link
Member

@ccarouge ccarouge left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@Whyborn Whyborn merged commit 0274a02 into main Jan 20, 2026
9 checks passed
@Whyborn Whyborn temporarily deployed to Gadi Prerelease January 20, 2026 00:46 — with GitHub Actions Inactive
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@JhanSrbinovsky JhanSrbinovsky JhanSrbinovsky approved these changes

@ccarouge ccarouge ccarouge approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@Whyborn @JhanSrbinovsky @ccarouge